Skip to content

fix: rename post-release sync branch to tmp/sync-main/{tag}#98

Open
hdamker wants to merge 1 commit intocamaraproject:release-automationfrom
hdamker:fix/rename-sync-branch
Open

fix: rename post-release sync branch to tmp/sync-main/{tag}#98
hdamker wants to merge 1 commit intocamaraproject:release-automationfrom
hdamker:fix/rename-sync-branch

Conversation

@hdamker
Copy link
Contributor

@hdamker hdamker commented Mar 1, 2026

What type of PR is this?

Bug fix / naming improvement

What this PR does / why we need it:

Renames the post-release sync PR branch from post-release/{tag} to tmp/sync-main/{tag}. The old name was confusingly similar to the permanent pre-release/{tag} pointer branch — both appeared as siblings in the branch list but have opposite lifecycles (pre-release/ is permanent, post-release/ is disposable after PR merge).

The tmp/ prefix clearly signals the branch is temporary, and sync-main/ describes its purpose (syncing release artifacts back to main).

Labels and descriptive text ("post-release sync") are unchanged — they describe the PR purpose, not the branch path.

Which issue(s) this PR fixes:

None (naming improvement found during E2E validation)

Special notes for reviewers:

Pure rename across 4 files. No behavioral changes. All 510 tests pass.

Files changed:

  • .github/workflows/release-automation-reusable.yml (branch name construction)
  • release_automation/scripts/post_release_syncer.py (branch name construction)
  • release_automation/tests/test_post_release_syncer.py (test strings)
  • release_automation/docs/technical-architecture.md (docs)

Changelog input

release-note
Rename post-release sync branch from post-release/{tag} to tmp/sync-main/{tag}

Additional documentation

docs

Avoids confusion with permanent pre-release/{tag} pointer branches.
The tmp/ prefix signals the branch is disposable after PR merge.
Labels and descriptive text unchanged.
Copy link
Contributor

@Kevsy Kevsy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM and makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants